This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Thanks to all - may I summarise? :-) ~Umberto Nongeroson 7.Nov.02 08:34 AM a Web browser Notes Client 6.0Windows XP
That Exchange produces broken MIME in some circumstances is clear. That at least one of these circumstances is likely to be fairly commonplace is also clear:
i.e. When an Outlook user sends email via an Exchange server and that email contains an in-line image (e.g. company logo) andthat email contains an attachment, the MIME rendering of the message makes the attachment an orphan, which a well behaved MUA will ignore.
Unfortunately, this is one of those situations where a bug in one vendor's product inconveniences only users of another vendor's product (all 9 billion of us, or whatever the correct number is - I know it's a lot). So I suspect the motivation to fix the bug may not be too high and this leaves open the possibility that other Notes users will in future receive email wherein an attachment has been lost in this way.
Indeed, this is likely to happen more frequently as I have recently seen evidence that a lot of Notes/Domino shops that had stuck at 4.6 are now moving directly to 6 and so more and more Notes users will soon be using the 6 client with native MIME.
All this really does for me is confirm my conviction that deploying a Notes/Domino messaging and collaboration solution for my company was exactly the right thing to do. It just works. Simple as that really.
Final question on this subject to Lotus/IBM: Given that broken MIME can and does show up in users' in-boxes (and will do so with increasing frequency in future), could the Notes client at least flag up a warning that the MIME it is trying to render is broken in some way? Users currently will have no clue that this is going on unless, like me, they know how to look at the MIME source and extract the orphaned part, which is hardly a user friendly operation to undertake. NB: I am not asking Notes to break the rules and show the attachment anyway (two wrongs do not make a right) - I am just saying that it would be nice if, when bad MIME shows up, the Notes client wasn't totally silent about it as it is now.
Thanks once again to everyone who helped and have a good day.
Return to top
. . Thanks to all - may I summarise? :-... (~Kelly Zekwebur... 7.Nov.02) 
Print this page
